Skip to main content

Known Issues with Single System Connections

Single System connections are built based on the concept of a Windows child session, which is a special loopback Remote Desktop Protocol (RDP) session that is tied to a user's existing session. Refer Windows Child Session in the Microsoft documentation for more information.

Windows child sessions are known to have issues with a Single System SUT (system under test) connections. Below are some known issues for Single system connections and methods for working around them.

Known issue: The SUT viewer window shows a black screen the first time you launch a Single System connection​

Issue: When you connect the first time, you might see a black screen.

Fix: Re-connecting will resolve this issue.

Known issue: The Google Chrome browser cannot launch without creating a new profile​

Issue: You cannot launch Google Chrome simultaneously from both the parent machine and the SUT because Windows restricts the launch of Chrome using the same profile between the parent session and the child SUT.

Fix: Create a new profile for Chrome, and launch it from the SUT.

Known issue: Single System connections cannot run as Windows services​

Issue: Single System connections are not workable when they are initiated from a Windows service because services run in a non-interactive session, which lacks access to user sessions. This prevents GUI interactions, remote desktop protocol (RDP) connections, and certain authentication mechanisms from functioning properly.

Fix: Enable a Windows child session from a Windows service by configuring the service to run under a specific user account instead of the default local system account. This allows the service to operate within an interactive user session, enabling GUI interactions and resolving limitations related to session isolation.

Known Issues: User account for Single System logon must be the same as the parent session​

  • The Single System connection must run under the same user account as its parent session (which is Eggplant Gateway/EPF installed) to inherit the necessary permissions, environment variables, and interactive session context.
  • If a different account is used, the child session may face access restrictions, GUI limitations, or authentication failures.

Known issue: User account access permission for Single System logon​

  • Single System connections require that the user account to have at least the below access permissions:

    • The user account must belong to the Administrator group.
    • The test machine must have Remote Desktop Services enabled.
    • The user account must be added to the Remote Desktop User Group.

  • Eggplant Gateway provides the epgw setup single-system command to help you set up user accounts with the following permissions:

    • Enables Windows child sessions on the local machine.
    • Adds the current logon user to the Remote Desktop User's Group.
    • Ensures Remote Desktop Services are running.
    • Enables Remote access to local settings.
    note

    The permissions granted with the above command do not include Administrator access, which the Single System logon requires. To grant Administrator access to a user account, you should work with your company's IT personnel for assistance.

    Run the command below to set up the above user account permissions as follows:

    1. Open a Windows shell in Administrator mode (which means launch the shell with Run as administrator).

    2. Change to your Eggplant Gateway directory and run the set-up command as follows:

    cd {path where the eggplant gateway located}
    ./epgw setup single-system
    note

    This command also runs when you install Eggplant Functional.

Last updated on